About the Harm State Standard (HSS)

Standard: Harm State Standard (HSS) Architecture: HAGA™ — Harm Governance
Architecture Governed Space: Harm State Governance

What It Governs

The Harm State Standard (HSS) governs the current state of a formally
governed Harm object after Harm Determination.

It establishes how Harm is:

identified by state

classified

maintained within a state

monitored

reassessed

and:

transitioned between states

HSS recognizes the canonical Harm States:

Emerging → Active → Escalating → Stabilized → Reduced → Recovering →
Residual → Resolved

These states do not require Harm to progress through a fixed linear
sequence. Why It Exists

Determining that Harm exists is not sufficient for governing what happens
afterward.

Harm may:

worsen

stabilize

decrease

recur

persist

recover

or:

remain after the original mechanism has stopped

Without explicit Harm State governance, a system may incorrectly
interpret:

lack of observation as absence of Harm

system repair as Harm Resolution

reduced visibility as reduced Harm

temporary improvement as Recovery

or:

Resolution as Finality

HSS exists to prevent those transitions from being assumed without a
governed basis. How It Works

HSS receives the:

Governed Harm Record

from HDS.

It then governs:

State Identification → State Classification → State Persistence → State
Transition → State Monitoring

The current Harm condition is classified using the materially supportable
state while preserving:

Harm identity

scope

duration

uncertainty

confidence

state history

and:

material State Signals

When the Harm materially changes, HSS records a governed State Transition
rather than automatically creating a new Harm object.

Conceptually:

Harm₁ / Active → Harm₁ / Escalating → Harm₁ / Stabilized → Harm₁ / Reduced

The state changes.

The governed Harm identity remains continuous. What It Prevents

HSS prevents shortcuts such as:

Harm Determination = Harm State

State Change = New Harm

No Observation = No Harm

Reduced Visibility = Reduced Harm

Mechanism Stopped = Harm Stopped

System Fixed = Harm Resolved

Contained Harm = Resolved Harm

Mitigated Harm = Resolved Harm

Recovery = Resolution

Resolved = Final

Predicted State = Current State

Simulated State = Actual State

It also prevents administrative, technical, organizational, session,
agent, or system boundaries from artificially resetting the state of
continuing Harm. Relationship to HAGA™

HSS occupies the lifecycle position between Harm Determination and Harm
Change & Propagation:

Harm Recognition → Harm Boundary → Harm Determination → Harm State → Harm
Change & Propagation → Harm Containment → Harm Mitigation → Harm Recovery
& Residual Harm → Harm Resolution & Finality

HDS asks:

Can Harm legitimately be determined to exist, and what governed Harm has
been established?

HSS asks:

What is the current governed state of that Harm?

HCPS then governs:

How does that Harm change, accumulate, compound, propagate, or cascade?

This creates an important boundary:

HSS governs the state of Harm. HCPS governs the dynamics through which
Harm changes.

Later HAGA™ standards govern Containment, Mitigation, Recovery, Residual
Harm, Resolution, and Finality. Use Case 1 — The Producing System Stops
but Harm Continues

An autonomous system produces a harmful physical or operational
consequence.

The system is immediately disabled and the unsafe behavior stops.

However, the affected subject continues to experience the Harm.

HSS does not classify the Harm as Resolved merely because the producing
mechanism has stopped.

The system may be:

Stopped

while the Harm remains:

Active

or later becomes:

Reduced → Recovering → Residual

The governing principle is:

Mechanism termination does not determine Harm State. Use Case 2 — Harm
Improves and Later Worsens Again

A governed Harm is initially:

Active

Following intervention, its condition becomes:

Reduced

and subsequently:

Recovering

Later, a material deterioration occurs.

HSS does not assume that improvement was permanent or create a new Harm
object automatically.

Where Harm identity remains continuous, the lifecycle may become:

Active → Reduced → Recovering → Active → Escalating

The complete trajectory remains attached to the same governed Harm.

The governing principle is:

Improvement does not terminate Harm identity, and recurrence does not
automatically create new Harm.

What It Does Not Govern

HSS does not determine whether Harm originally exists, perform Harm
Recognition, establish or modify the Harm Boundary, or redo formal Harm
Determination.

It does not govern the mechanisms through which Harm:

accumulates

compounds

propagates

or:

cascades

It does not perform Harm Containment or Mitigation, govern Recovery or
Residual Harm determination, establish Harm Resolution or Finality,
determine general causation, assign accountability or responsibility,
determine liability, or govern claims or compensation.

Those functions remain within their respective HAGA™ stages or adjacent
OOF® architectures.

Why It Matters

Harm exists through time.

A Harm governance system therefore needs more than a record that Harm once
existed. It needs to know what condition that Harm is in now and how that
condition has changed.

This becomes particularly important where Harm is:

long-duration

intermittent

distributed

collective

latent

cross-domain

or:

persistent after the original mechanism has ended

HSS creates the methodological continuity required to govern that changing
reality without repeatedly confusing Harm State with Harm existence.

Closing Statement

A Harm may remain the same governed Harm while almost everything about its
current condition changes.

It may worsen, stabilize, diminish, recur, recover, or persist residually
without losing its identity.

HSS governs that changing condition so that neither technical boundaries
nor temporary appearances can silently redefine the state of Harm.

Determination establishes the Harm. HSS governs what state that Harm is in
now.